Comment Re:Crap in, crap out (Score 1) 69
Wild off the cuff guess stat. 80% of content being consumed by LLM is untrustworthy, opinion, wrong, brain farts.
This is just numerology masquerading as evidence. When the opening move is “wild off the cuff guess” and the next move is a percentage, that is not data analysis. That is a vibe cosplaying as rational thought. Training data quality is a real problem. So are filtering, curation, retrieval, evals, domain tuning, and human review. “The web contains garbage” does not prove that models cannot extract useful structure from it. Compilers consume source written by humans too; somehow LLVM survived Stack Overflow.
Anyone who believes LLM will lead to Gen AI doesn't get the tech or has an incomplete definition of Gen AI. We really need a new Turing test, we kinda cheated the test with LLM, made a parrot instead of a person.
Now you are just playing bait-and-switch with definitions. For AGI, say AGI. For generative AI, the ship has already left port. And “parrot or person” is the false dichotomy at the center of the whole performance. LLMs do not need to be conscious citizens with library cards to be useful systems. The question in this thread is not whether ChatGPT has a soul. The question is whether particular copying, training, output, and platform design cross copyright lines. Your parrot/person routine is theatrical fog, and when it's this thick and obvious, it is usually because somebody is trying to obscure their bias.
The principal flaw of LLM AI as a business is that producing content wasn't a problem we needed to solve. We were drowning in the stuff already.
Nice product-market strawman. “Producing content” is not the only use case, nor even the most interesting one. Summarizing 80 pages, interrogating logs, turning vague specs into tests, translating formats, drafting boring boilerplate, extracting facts from PDFs, building code scaffolding, and helping users query systems in natural language are not solved by shouting “more content!” Databases were not pointless because we already had files. When new technology disrupts an ecological niche, the people pushed out of the niche start lining up strawmen in defense. Your argument here is older than the buggy whip makers who whined that automobile makers were killing their art.
LLMs give a great search and summary feature, but I don't see a way to monetise that with ads like google does...
So...one business model treated as destiny. Treating ad-tech as the only viable business model shows a massive lack of imagination. Google-style ads are not how enterprise software scales, and are not the only way LLMs makes money. Enterprises buy latency reduction, workflow automation, support deflection, developer acceleration, compliance review, document analysis, and boring internal productivity nobody will ever put in a Super Bowl commercial. Your Copilot adoption anecdote may be true in your shop, but an anecdote is a packet capture from one subnet. Generalizing from that to the whole network is bad telemetry.
I work with a lot of ambitious go getters, who would I promote? The one who leans on AI to produce some samey looking dross, or the one who can innovate and communicate independently...
More false dichotomies, this time it's tool use recast as moral failure. The choice is not AI dross versus independent genius. The choice is bad judgment versus good judgment. Good people already use search engines, spreadsheets, IDEs, compilers, code review, dashboards, staff work, LLMs, and lawyers. A leader who pastes "samey" AI sludge is weak. A leader who uses AI to explore options, pressure-test assumptions, and communicate faster has not been compromised. The bottleneck is still judgment. A Hollywood director who uses AI to storyboard five different versions of a scene is still being creative; he is leveraging the AI samey-ness you are decrying to get a more fine-grained look at the scene before he commits resources to filming it. That is a win for both the audience and the bean counters back at the studio HQ.
Then there is a phenomenal trust issue...
Spare us the sermon. These are real issues; nobody denies that trust, provenance, validation cost, confidentiality, copyright, and vendor terms are all real deployment concerns. They belong on the checklist. But welding them to “employees getting dumber” is no different from when my high school principal tried to forbid calculators and had to be taken to court to make him join the twentieth century. That was during the Carter administration, btw -- your argument is fifty years old. We already review junior work, consultant work, SQL migrations, security patches, vendor output, and code changes. The adult answer is measurement, sandboxing, governance, and evals, not declaring every inference engine a cognitive tapeworm.
And this is where the actual legal story matters. The Cox decision makes it harder to pin contributory liability on a provider merely because it knew infringement was happening downstream. Intent matters. Inducement matters. Tailoring matters. That is why NYT is now aiming at Microsoft’s alleged role in building and operating the machinery, not just shouting “AI cloud bad.” That is the real fight. Not parrots. Not personhood. Not whether Bob in accounting wrote a dull memo with Copilot.
Nope.
“Nope” is not an argument. It is just a vibe with a punctuation mark.
I don't doubt there are niche specialist applications... but specialise and grow your own... Don't end up dependent on a supplier...
You make the accidental good point. Specialize. Keep sensitive data controlled. Avoid lock-in. Prefer vetted corpora. Use local or open models where they fit. Put APIs behind abstraction layers. Maintain exit ramps. Do human review on high-stakes output. Yes. Absolutely. That is not an anti-AI argument; that is ordinary systems engineering and vendor hygiene with the cloud invoice scotch-taped to the front.
So, in a bucket: you took a narrow copyright-liability story and stapled to it every anti-AI talking point from the break room bulletin board. Some of your concerns survive cross-examination, but most of the big claims you are making die from false dichotomy, anecdote laundering, and category confusion: AGI, GenAI, search, copyright, trust, productivity, and cloud lock-in all blended into one rhetorical smoothie. The law is asking whether Microsoft induced infringement or tailored services to it, and you hijacked that into whether parrots can be people.